home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
auditing
/
newscn.exe
/
WHATS.NEW
< prev
Wrap
Text File
|
1993-11-03
|
5KB
|
107 lines
What's new in v1.3a from v1.2a
---------------------------------------------------
Multiple /I parameters are now allowed (up to 10).
Fixed bug in getting DOS version on some PCs.
Fixed I/O port alerts to display port address in hex.
Fixed bug in figuring unused free space on hard disk.
Alerts now work for master software list by setting default SWI alerts
There are only two alerts that currently work for software inventory:
1) Found (Added) alert, which will alert you to new software on a node
2) Removed alert, which will alert you to software deleted from a node.
You can now set the minimum alert level which triggers alerts to NCI's
LANAlert with the following environment variable: BV_LANALERT_LEVEL.
"SET BV_LANALERT_LEVEL=0" disables alerts to LANAlert;
"SET BV_LANALERT_LEVEL=5" means only alert level 1 through 5 will get sent.
What's new in BVequip v1.3b
------------------------------------------------------------------
Fixed bug in BVEQUIP and BVDIAG which resulted from a problem with
3COM's Etherlink III driver used on an IBM's PS/2 Model 55SX.
What's new in BVequip v1.3c/d and BVscan 1.3c/d
------------------------------------------------------------------
Fixed bug in BVEQUIP and BVDIAG which resulted from a problem with
3COM's Etherlink III driver used on an IBM's PS/2 Model 55SX.
/F will force software inventory alerts even if software inventory
interval for the node is set to NEVER.
Fixed bug with comments not being ingored in string searches
Turned on software inventory alerts (as in last read me file) -- was
disabled while beta testing.
Fixed environment variable update bug. When environment variables
changed, they were not always being updated in the environment
variable list for a node and change alerts were not being generated.
Fixed problem with "Wierd CD ROM" display message when auditing
CD ROM Drives.
Fixed problem with comments in strings searches being case sensitive.
Now, the case (upper/lower) of the comments are ignored and comments
specified in string search parameters are handled properly.
Fixed problem with alert actions for new nodes. If you had an alert
acount without an alert level, the action was not happening. This
problem has been fixed.
Change to file audit intervals. If the configuration parameters
for the file audit have been changed since the last audit, the file
audit will be triggered even if the audit interval has not been reached.
A bug in software inventory alerts has been fixed which allows
software inventory alerts to now be properly generated. In addition,
two new alert types have been added for software inventory that did
not work previous to this version: Changed and Moved alerts.
To summarize software inventory alerts, here are the 4 alerts for
software inventory:
1) Found (Added) alerts, for new software added on a node
2) Removed alerts, for software which was been deleted from a node.
3) Changed alerts, for changes in software files' size/date/time/attributes.
4) Moved alerts, for software files moving locations on a user's disk.
Software Inventory Alerts are configured in the WAM Setup module
from the BVequip/BVscan Setup menu. Look under Setup Alerts ->
Alert Defaults -> Software Inventory. Here you can define the
alert levels and actions for the 4 software inventory alerts.
In the current version, these "defaults" become the active alert
configuration for all software inventory alerts.
What's new in BVequip v1.3e and BVscan 1.3e
------------------------------------------------------------------
Fixed bug in BVEQUIP.EXE "/X" parameter not preventing unknown
network numbers from being added to the WAM database.
Fixed bug in BVSCAN.EXE which would occur if the max file size
specified for a File Audit configuration (e.g., when auditing *.INI
and specifying a maximum file size to be audited). If the configured
max file size was greater than 2,147,483,647 bytes, BVSCAN.EXE
would not audit the file. This has been fixed, and the maximum
file size that you can use when configuring file audits is now
4,294,967,295 bytes (as you always saw in the error message if
you tried to type in a number higher than this into the max file
size field).
BVEQUIP.EXE now counts drives that have been partitioned but
not formatted as "Unknown" drive types. Alerts have been trimmed-
down so that changing the drive type only results in one alert
instead of several. Device drivers that look like DOS drive letters,
but that cannot identify what kind of media they are, are now
referred to as type "Unknown."
Added enhanced code to BVEQUIP.EXE to identify 386SX vs. 386DX.
Modified BVSCAN.EXE so that if there is not enough memory to run the
full audit (but is enough memory to start the program) an alert
will be generated [in addition to the message that you used to get].